-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dex: evict excess of liquidity positions #4511
Conversation
7917244
to
f733274
Compare
I have tested this manually on a devnet using a tweaked version of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks good to me. nice work! i found a bug in our "recently accessed assets" logic, but i see that it comes from preexisting code, so i don't consider it blocking this change, despite it being a part of the diff.
the logic looks good, and the refactorings along the way have great side-effects. 🙂
Co-authored-by: katelyn martin <[email protected]> Signed-off-by: Erwan Or <[email protected]>
Co-authored-by: katelyn martin <[email protected]> Signed-off-by: Erwan Or <[email protected]>
this is a small change. this is a nice property about our data model, i.e. that an owned copy of the dex parameters may be used to make routing parameters. let's make that relationship explicit by putting it into a `From<T>` impl, and pulling it out of the `StateReadExt` logic.
Description
This PR:
StateWriteExt
and trim the dex component's public interfaceIssue ticket number and link
Final step to implement #4077
Checklist before requesting a review
If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: